[release/2.14] Remove CUDA 13.4 from the binary build matrix - #8601
Merged
atalman merged 1 commit intoAug 21, 2026
Conversation
CUDA 13.4 is not shipping in the 2.14 release, so the release branch should not be building or testing it. The `release` channel already excluded 13.4; this drops it from the `nightly` and `test` channels too, along with the supporting arch/cudnn entries, so nothing on release/2.14 generates a 13.4 job. Changes in `tools/scripts/generate_binary_build_matrix.py`: - `CUDA_ARCHES_DICT`: drop `13.4` from `nightly` and `test` - `CUDA_CUDNN_VERSIONS`: drop the `13.4` entry - `CUDA_AARCH64_ARCHES`: drop `13.4-aarch64` - `CUDA_ARCHES_NO_WINDOWS`: now empty (13.4 was its only member) Test assets regenerated for the four affected matrices; each loses exactly the 8 CUDA 13.4 entries (one per Python version) with no other change: - `build_matrix_linux_wheel_cuda.json` 56 -> 48 - `build_matrix_linux_wheel_cuda_norocm.json` 40 -> 32 - `build_matrix_linux_wheel_nocpu.json` 48 -> 40 - `build_matrix_linux_wheel_xpu.json` 40 -> 32 The macOS and Windows assets are unchanged, as expected: macOS has no CUDA builds and 13.4 was already excluded from Windows. `tools/pkg-helpers/tests/test_cuda.py` still parametrizes over 13.4, which is left alone deliberately -- it exercises version-string sanitization on an arbitrary version and does not depend on the build matrix.
|
@atalman is attempting to deploy a commit to the Meta Open Source Team on Vercel. A member of the Team first needs to authorize it. |
huydhn
approved these changes
Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CUDA 13.4 is not shipping in the 2.14 release, so
release/2.14should not build or test it. Thereleasechannel already excluded 13.4; this drops it from thenightlyandtestchannels too, plus the supporting arch/cudnn entries, so nothing on this branch generates a 13.4 job.This targets
release/2.14only. The companion change for the same branch is in pytorch/pytorch.Changes
tools/scripts/generate_binary_build_matrix.py:CUDA_ARCHES_DICT13.4fromnightlyandtest(releasealready lacked it)CUDA_CUDNN_VERSIONS13.4entryCUDA_AARCH64_ARCHES13.4-aarch64CUDA_ARCHES_NO_WINDOWS13.4was its only memberTest assets regenerated for the four affected matrices. Each loses exactly the 8 CUDA 13.4 entries (one per Python version), with zero additions and zero non-13.4 removals:
build_matrix_linux_wheel_cuda.jsonbuild_matrix_linux_wheel_cuda_norocm.jsonbuild_matrix_linux_wheel_nocpu.jsonbuild_matrix_linux_wheel_xpu.jsonThe macOS and Windows assets are unchanged, as expected — macOS has no CUDA builds, and 13.4 was already excluded from Windows via
CUDA_ARCHES_NO_WINDOWS.Test Plan
Test Result
11 passed. I also diffed the regenerated assets structurally (parsed JSON, compared entry lists) to confirm every removed entry carries a13.4/cu134marker and nothing else changed.Notes for the reviewer
tools/pkg-helpers/tests/test_cuda.pystill parametrizes over13.4. Left deliberately — it exercises version-string sanitization against an arbitrary version and has no coupling to the build matrix.tools/tests/update_test_assets.shthat I hit and worked around rather than fix here, since they are out of scope: it invokespython(notpython3), and its three--package-type condalines fail withKeyError: 'conda'because conda support was removed from the generator. Because the redirect truncates before the command fails, running the script as-is empties the conda assets. It also emits single-line JSON while the checked-in assets areindent=2, so a naive run reformats every file. Worth a follow-up.